7 matches found
CVE-2026-32709
The CVE describes an unauthenticated path traversal in PX4 Autopilot MAVLink FTP that allows any MAVLink peer to read, write, create, delete, and rename arbitrary files on the flight controller filesystem. On NuttX targets, attacker-supplied paths bypass sanitization due to an empty FTP root, whi...
CVE-2024-29460
CVE-2024-29460 affects PX4 Autopilot v1.14.0, specifically the mission_block.cpp component. The issue enables an attacker with local access to manipulate the flight path via the home point, potentially causing a drone crash. Multiple connected sources (NVD, Red Hat) corroborate that the vulnerabi...
CVE-2026-32743
PX4 Autopilot versions 1.17.0-rc2 and earlier are affected by a Stack-based Buffer Overflow in the MAVLink log request handling via MavlogHandler. The LogEntry.filepath buffer is 60 bytes, and paths are parsed with sscanf without a width specifier, allowing overflow when a longer path is provided...
CVE-2024-38951
CVE-2024-38951 describes a buffer overflow in PX4-Autopilot v1.12.3 that allows an attacker to cause a Denial of Service via a crafted MavLink message. The Red Hat/NVD/OSV entries confirm the same description; PT-Security suggests a temporary mitigation: disable handling of MavLink messages until...
CVE-2026-32713
CVE-2026-32713 affects the PX4 Autopilot MAVLink FTP subsystem. A logic error in session validation (using boolean AND instead of OR) permits BurstReadFile and WriteFile operations to proceed with invalid sessions or closed file descriptors, enabling an unauthenticated attacker to put the FTP sub...
CVE-2026-32707
CVE-2026-32707 affects PX4 Autopilot with the tattu_can module. A stack buffer overflow results from an unbounded memcpy in the multi-frame assembly loop, allowing stack memory overwrite when crafted CAN frames are processed. In affected deployments where tattu_can is enabled, a CAN-injection cap...
CVE-2026-32705
Summary: The CVE affects the PX4 autopilot BST telemetry driver. Before version 1.17.0-rc2, the BST device can report an oversized dev_name_len, and the driver writes a string terminator without bounds, causing a stack overflow that can crash the task or enable code execution. Root cause: device-...